fix: add ",z" SELinux relabel to CA cert bind mounts#21
Open
cfis wants to merge 1 commit into
Open
Conversation
cfis
force-pushed
the
fix/selinux-relabel-flag
branch
from
447f540 to
6eed5da
Compare
Author
|
Rebased to current |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On SELinux-enforcing hosts (e.g. Fedora + rootless podman), bind-mounted CA cert files keep their host label (
user_tmp_t) and the container process can't read them — surfacing as "self-signed certificate detected" or "error setting certificate file" inside containers spawned viaapplyContainerConfig.Appending
,z(shared SELinux relabel) to the two-vmounts lets podman relabel the cert files tocontainer_file_tat mount time. I think this is a no-op on macOS and non-SELinux Linux, so is safe to apply unconditionally.